Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1775

reference: 244-tree-1
name: 1775
tree-preservation-order: undefined
244-tpo-1
uprn
address-text
point: POINT (-1.004172 50.855011)
geometry: MULTIPOLYGON (((-1.004130 50.855006,-1.004132 50.855015,-1.004137 50.855022,-1.004147 50.855028,-1.004159 50.855032,-1.004172 50.855034,-1.004197 50.855029,-1.004206 50.855023,-1.004213 50.855015,-1.004215 50.855007,-1.004213 50.854999,-1.004207 50.854991,-1.004198 50.854985,-1.004186 50.854981,-1.004173 50.854980,-1.004160 50.854981,-1.004148 50.854985,-1.004138 50.854991,-1.004132 50.854998,-1.004130 50.855006)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL